Redundant Battery Management System Architecture

ABSTRACT

A vehicle can include a battery architecture configured to provide electrical power to motors, accessories, and other components of the vehicle. The architecture can include a controller coupled to multiple battery units. Each battery unit can include a battery and a battery management system. Additionally, each battery unit can be coupled to a controller and to other battery units. Through the use of redundant coupling and redundant data transmitted to and from the controller, battery units, and other components, the architecture can detect a fault and continue to operate while providing an indication of the fault.

BACKGROUND

A vehicle can use batteries to provide energy to operate the vehicle.Operations can include providing electrical power to one or moreelectric motors, sensors, accessories available for use by passengers ofthe vehicle, and/or other vehicle systems. In order for the vehicle tooperate reliably, some or all of these vehicle systems rely on areliable supply of battery power. However, during the course ofoperation, degradation of performance or failures can occur, leaving thevehicle significantly limited or inoperable. For example, in someconventional battery system architectures, failure of a battery, abattery controller, or a coupling to a battery can result in aninoperable system or vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical components or features.

FIG. 1 depicts an example architecture of a redundant battery managementsystem (BMS) architecture.

FIG. 2 depicts an example system for implementing a redundant BMSarchitecture as well as an example environment of a vehicle maneuveringtoward a recharging station.

FIG. 3 is a schematic view of an example vehicle comprising a bodymodule, a pair of drive modules disposed at opposite ends of the bodymodule, and a battery unit disposed within or coupled to each drivemodule.

FIG. 4A depicts an example architecture of a redundant BMS architectureusing a ring configuration.

FIG. 4B depicts an example architecture of a redundant BMS architectureusing a mesh configuration.

FIG. 5 depicts an example process for receiving battery data andinstructing battery units.

FIG. 6 depicts an example process for generating battery data andtransmitting battery data.

FIG. 7 depicts an example process for determining a fault condition.

DETAILED DESCRIPTION

This disclosure describes systems, methods, and apparatuses forproviding a redundant battery management system (BMS) architecture(e.g., a communication architecture) in a vehicle. As discussed above,conventional battery system architectures can result in an inoperablevehicle in some fault conditions. For example, in a conventional batterysystem architecture, the failure of a battery, a battery controller, acommunication link therebetween, or a coupling to a battery can cause afailure of the entire system. Such architectures may be unsuitable forautonomous vehicles or any other type of electrically powered device orsystem that requires a certain degree of robustness.

This disclosure is generally directed to systems, methods, andapparatuses for a redundant BMS architecture, e.g., a communicationarchitecture. In some instances, a system for providing a redundant BMSarchitecture can include one or more controllers used to issue commandsto other components (e.g., adjust a load connected to the output, suchas set torques of motor controllers, connect or disconnect a battery,etc.), communicate states or parameters of one or more components (e.g.,a battery), as well as determine if a fault condition has occurred inthe system. The controller(s) can also be configured to provideindications of a fault. In some instances, the controller can calculatea capacity or a limit of the system (e.g., a maximum number of currentor power provided by one or more batteries) based on data received fromother components.

The redundant BMS architecture of this disclosure can also include afirst battery unit and a second battery unit, though any number of unitsis contemplated. In some instances, each battery unit can contain abattery and a BMS. The battery can store energy for use by the redundantBMS architecture and/or an electrical load. The BMS can monitor thestatus of the battery and/or the battery unit including, but not limitedto, a state of charge, a voltage level, a current draw, a power level,an internal resistance, and the like. Additionally, the BMS can beconfigured to transmit and receive battery data as well as receiveoperational commands.

In some instances, the redundant BMS architecture can be implementedsuch that the controller is electrically and/or communicatively coupledby a coupling to the first battery unit and/or the second battery unit.The coupling can allow the controller to communicate with the firstbattery unit and/or the second battery unit. In some instances, thecontroller can transmit operational commands to the first battery unitand/or the second battery unit. For example, such a command may compriseeither an “ON” or “OFF” designation such that the BMS of the batteryunit appropriately connects or disconnects the battery to a common line(which may be for charging or discharging over a load). In someinstances, the controller can transmit other operational commands asneeded for operation of the vehicle or device. As several non-limitingexamples, such commands may comprise a drive command (e.g., sending atorque request to motor controllers), a braking command, a sleepcommand, etc. In some instances, the controller can transmit batterydata to the first battery unit and/or the second battery unit. Thebattery data can include current limit data, power limit data, voltagelimit data, temperature data, connection data, a battery state, a systemstate, or a battery status, though any other information regarding aparameter of the battery is contemplated. In some instances, the batterydata can include impedance data (such as internal resistance) or otherdata related to the battery.

In some instances, the battery data can include aggregate battery data.In some examples, the aggregate battery data can represent a currentthat can be provided by battery units in the power system, for example,as an aggregate battery limit. To generate and/or calculate theaggregate battery data, the BMS architecture can include redundantcommunication pathways for data to be exchanged between variouscomponents of the vehicle. For example, in some instances, the secondbattery unit can transmit second battery data to the controller and tothe first battery unit, the controller can transmit the second batterydata to the first battery unit, and the first battery unit can transmitfirst battery data to the controller. The first battery unit can use thesecond battery data to generate and/or calculate first aggregate batterydata and transmit the first aggregate battery data to the controller. Insome instances, the transmission of data can occur concurrently and/orin different order without affecting the operation of the system. Insome instances, the second battery unit can use the first battery datato transmit second aggregate battery data to the controller. In someinstances, the controller can receive first aggregate battery dataand/or second aggregate battery data. In some instances, the controllercan compare the first aggregate battery data and the second aggregatebattery data and select the lower aggregate battery data, the higheraggregate battery data, or either aggregate battery data if the firstaggregate battery data and the second aggregate battery data aresubstantially similar. In some instances, the controller can select thelower aggregate battery data to operate in a conservative configurationto prevent, for example, damage to a component of the system. In otherinstances, the controller can select the higher aggregate battery datato operate in a higher performance configuration. Operations of avehicle component, such as a drive motor, can be controlled inaccordance with the aggregate battery data.

In some instances, the battery unit can transmit a state or status ofone or more of the battery unit, the battery, the BMS, or the system tothe controller. The states can be a sleep state, a standby state, adriving state, a charging state, or a shutdown fault state. In someinstances, other states can be implemented as needed. The status can bean “okay” status (e.g., a normal operating status), a “do not start”status (e.g., a low-level fault that can indicate, in some instances, asingle point fault that does not impact performance or safety), an “endmission” status (e.g., a medium-level fault that can indicate, in someinstances, a fault that can impact performance and/or safety operationpersists beyond a threshold operation), or a “stop immediately” status(e.g., a high-level fault that can, in some instances, disable continuedoperation). In some instances, other statuses can be implemented asneeded.

In some instances, the first battery unit can be coupled to the secondbattery unit. In such an instance, the controller can be coupled to thefirst battery unit and the second battery unit and each battery unit canbe coupled to the other battery unit. In some instances, the firstbattery unit can transmit first battery data to the second battery unitwithout transmitting the first battery data to the controller. In someinstances, the first battery unit can transmit first battery data to thesecond battery unit by directly transmitting to the second battery unitas well as through the controller. In such an instance, the secondbattery unit can receive the first battery data from the first batteryunit as well as from the controller.

In some instances, the redundant BMS architecture can include a thirdbattery unit or more battery units. In such an implementation, thecontroller can be coupled to each battery unit in the BMS architecturesuch as in a hub-and-spoke topology. In other instances, the controllercan be coupled to a subset of the available battery units. In someinstances, the controller can be coupled to each battery unit and eachbattery unit can be coupled to every other battery unit such as in afull mesh topology. In other instances, the controller can be coupled toa subset of the available battery units and some of the battery unitscan be coupled to some or all of the other available battery units. Insome instances, all battery units and any one or more controllers may beconnected as a ring and pass relevant information (including aggregates)through the ring such that any one component (BMS or controller) mayperform any check with respect to faults, limits being exceeded, or thelike. As discussed above, the controller can transmit operationalcommands as well as transmit and receive battery data. Additionally, thebattery units can transmit and receive battery data.

The methods, apparatuses, and systems described herein can beimplemented in a number of ways. Example implementations are providedbelow with reference to the following figures. Although discussed in thecontext of an autonomous vehicle, the methods, apparatuses, and systemsdescribed herein can be applied to a variety of systems using electricalpower, and is not limited to autonomous vehicles. In another example,the methods, apparatuses, and systems may be utilized in an aviation ornautical context.

FIG. 1 depicts an example architecture 100 implementing a redundant BMSarchitecture. As shown in the figure, the architecture 100 includes anexecutive controller (EC) 102 (also referred to as a controller). Insome instances, multiple controllers can be used. The EC 102 can becoupled to a first BMS 104 and a second BMS 106. Although not shown inFIG. 1, the first BMS 104 can be included in a battery unit along with abattery or can be included separately from the battery unit. Similarly,the second BMS 106 can be detached from a second battery unit or placedwithin the second battery unit. In some instances, the first BMS 104 andthe second BMS 106 can be placed within the same battery unit. In someinstances, any number of BMS units can be used, although in general, oneBMS can be used to monitor and/or control a single battery unit. The EC102 can be coupled to the first BMS 104 through a first coupling or afirst drive controller area network (CAN) 108. The EC 102 can also becoupled to the second BMS 106 through a second coupling or a seconddrive CAN 110. The redundant BMS architecture 100 can also implement acoupling or an interpack CAN 112 coupling the first BMS 104 to thesecond BMS 106.

As shown in FIG. 1, the first BMS 104 can be coupled to the EC 102 viathe first drive CAN 108. Additionally, the second BMS 106 can be coupledto the EC 102 via the second drive CAN 110. In such a case, the firstBMS 104 can transmit data 114 to the EC 102 via the first drive CAN 108.In some instances, the data 114 can include first battery data from thefirst BMS 104 to the EC 102. Additionally, using the second drive CAN110, the second BMS 106 can transmit data 116 to the EC 102. The EC 102can be configured to transmit the first battery data to the second BMS106 and transmit the second battery data to the first BMS 104.

The first battery data and/or the second battery data can comprise datasuch as limit data. In some instances, a battery unit, a battery, or aBMS can have an operating limit or a maximum limit. The operating limitcan indicate a limit that would typically not be surpassed whileoperating under normal conditions. A maximum limit could indicate amaximum before damage or failure occurs. The types of limits can includecurrent limits, power limits, voltage limits, operational limits, andthe like.

The first battery data and/or the second battery data can also includeconnection data. In some instances, via communication protocols, thefirst BMS 104 and/or the second BMS 106 can detect data loss and/orcorruption. The first BMS 104 and/or the second BMS 106 can transmitthis information as connection data to the EC 102 or to other BMS unitsand/or components.

The first battery data and/or the second battery data can also include astate and/or a status. The state can be a system state, battery state, aBMS state and/or a battery unit state. The states can include a sleepstate (e.g., the battery is not providing power and the vehicle isinactive), a standby state (e.g., the battery is ready to provide powerand waiting for further instructions), a driving state (e.g., thebattery is providing power and/or is actively responding to maneuveringcommands), a charging state (e.g., the battery is receiving electricalpower), and/or a shutdown fault state (e.g., the battery has shut downdue to a fault as is waiting for assistance, attention, and/ormaintenance). In some instances, other states can be implemented.Additionally, the status can be a battery status, a BMS status and/or abattery unit status. The statuses can include an “okay” status, a “donot start” status, an “end mission” status, and/or “a stop immediately”status, as described above. In some instances, other states can beimplemented.

The first battery data and/or the second battery data can also includeimpedance data. The impedance data can be real-time impedance data thathas been measured or determined by the first BMS 104 and the second BMS106, respectively. In some instances, the impedance data can be staticdata based on an initial configuration of a battery, BMS, or batteryunit (e.g., by using a lookup table based on, for example, temperature,state of charge, current draw, or the like).

In some instances, the first BMS 104 can be configured to determine afirst aggregate battery data and transmit the first aggregate batterydata to the EC 102. Additionally, in some instances, the second BMS 106can be configured to determine a second aggregate battery data andtransmit the second aggregate battery data to the EC 102. The firstaggregate battery data and/or the second aggregate battery data caninclude any combination of data or calculation(s) of data including anyof the battery data described above. In some instances, the firstaggregate battery data can include a first aggregate current limit(e.g., a first aggregate limit). In some instances, the second aggregatebattery data can include a second aggregate current limit (e.g., asecond aggregate limit). Such current limits may be indicative of, forexample, the limit of current which can be delivered by the combinedbattery sources. In some instances, the first aggregate current limitcan comprise a sum of the first current limit and the second currentlimit. In some instances, the first aggregate current limit can comprisea table lookup based on a characterization of the batteries and usingany one or more of a temperature, voltage, state of charge, or currentlimits as lookup values to the table. In some instances, the firstaggregate current limit can comprise a dynamic current limit based onthe impedance data or the current data determined by the first BMS 104and/or the second BMS 106. In some examples, such a dynamically limitmay be based on, for example, a feedback loop comprising observedcharacteristics of the first battery. In some instances, the observedcharacteristics can include an impedance, a slew rate, and/or anovershoot of the first battery. Such aggregate limits may be similarlycalculated by the second BMS 106.

The first BMS 104 can also be configured to transmit data 118 to thesecond BMS 106 using the interpack CAN 112. Additionally, the second BMS106 can be configured to transmit data 118 to the first BMS 104 usingthe interpack CAN 112. The data can comprise similar data as data 114and data 116 transmitted by the first BMS 104 and the second BMS 106respectively.

In some instances, the redundant BMS architecture 100 can provide acertain degree of fault tolerance. By way of example, the interpack CAN112 can be severed, resulting in an inability of the first BMS 104 totransmit data to the second BMS 106 directly using the interpack CAN112. However, the data 118 sent along interpack CAN 112 is substantiallysimilar to the data 114 sent along the first drive CAN 108. Asillustrated in FIG. 1, portions of data 114 are then sent via the seconddrive CAN 110 to the second BMS 106. As such, all components (the firstand second BMSs 104, 106 and the EC 102) all have the same data as ifthe interpack CAN 112 hadn't been severed. Therefore, in thisillustration, the redundant BMS architecture 100 can continue normaloperation. However, as the first BMS 104 is no longer able to receivethe data 118 from the second BMS 106, the aggregate limit calculated bythe first BMS 104 would be lower than an actual aggregate. Because of,for example, this difference, the EC 102 could determine a faultcondition, in this illustration, that the interpack CAN 112 is severed,and, in some instances, generate an indication of the fault condition.

By way of another example, either of the first drive CAN 108 or thesecond drive CAN 110 can be severed (or otherwise damaged), resulting inan inability of the second BMS 106 to transmit data to the EC 102directly using the second drive CAN 110. The data 118, however, sentalong the interpack CAN 112 is substantially similar to the data 116sent along the second drive CAN 110. Therefore, in this illustration,the redundant BMS architecture 100 can continue normal operation. Asabove, differences in aggregate limits from the first and second BMSs104, 106 received by the EC 102 may be indicative of such a fault andthe EC 102 may respond accordingly.

FIG. 2 depicts an example system 200 for implementing a redundant BMSarchitecture as well as an example environment of a vehicle 202maneuvering toward a recharging station. The vehicle 202 may be anyconfiguration of vehicle, such as, for example, a sedan, a van, a sportutility vehicle, a cross-over vehicle, a truck, a bus, an agriculturalvehicle, and a construction vehicle. The vehicle 202 may be powered byone or more electric motors, one or more internal combustion engines,any combination thereof (e.g., a hybrid power train), and/or any othersuitable electric power sources. For the purpose of illustration, thevehicle 202 is an at least partially electrically powered vehicle havingtwo battery units configured to provide the vehicle 202 with electricalpower.

The vehicle 202 can include a first battery unit 204 which can comprisea first battery 206 and a first battery management system (BMS) 208. Insome instances, the first battery unit 204 can be communicativelycoupled to a second battery unit 210. The second battery unit 210 cancomprise a second battery 212 and a second BMS 214.

In some instances, the vehicle 202 can include an vehicle computingsystem 216. The vehicle computing system 216 can be communicativelycoupled to the first battery unit 204 and/or the second battery unit210, in accordance with the discussion provided in FIG. 1.

The vehicle 202 can also include an executive controller 218 which caninclude processor(s) 220 and memory 222 communicatively coupled toprocessor(s) 220. In some instances, the executive controller 218 orcomponents within the executive controller 218 can be implemented withinthe vehicle computing system 216. In other instances, the vehiclecomputing system 216 can be implemented within the executive controller218. In some instances, components within the executive controller 218can be implemented within the first battery management system 208 and/orthe second battery management system 214.

In the illustrated example, the memory 222 of the executive controller218 stores an operational command component 224, a limit comparisoncomponent 226, a fault detection component 228, system controller(s)230, a battery state component 232, a battery status component 234 and alimit aggregation component 236. Although discussed in the context ofthe memory 222, the executive controller 218 may include a processor andmemory that may implement one or more of the components 224, 226, 228,230, 232, 234, and 236. In some instances, the executive controller cancomprise the processor(s) 220 and the memory 222.

The operational command component 224 can be configured to generatecommands transmitted by the executive controller 218. The commands canbe, in some instances, a shutdown command, a drive command, a chargecommand, or a sleep command. The executive controller 218, can becommunicatively coupled to the first battery unit 204 and/or the secondbattery unit 210 and transmit the commands to the first battery unit 204and/or the second battery unit 210.

The limit comparison component 226 can compare limits received at theexecutive controller 218. As discussed above, the first batterymanagement system 208 can transmit first battery data to the executivecontroller 218 and the second battery management system 214 can transmitsecond battery data to the executive controller 218. The first batterydata and the second battery data can include operational data such astemperature data and/or first limit data and second limit data,respectively, such as current limit data, power limit data, and/orvoltage limit data. In at least some examples, such limit data comprisesaggregate limits calculated by each of the first and second BMSs 208,214 based on the limit of their own battery, as well as limits receivedfrom the other BMS. In other examples, such aggregates may be determinedby the executive controller 218 based on data of the first and secondbatteries 206, 212 sent by the BMSs 208, 214. The limit comparisoncomponent 226 can compare the values of the first limit data (e.g. firstaggregate data) and the second limit data (e.g. second aggregate data)and determine which has a higher or a lower value. In at least someexamples, the executive controller 218 may choose the lower value so asto provide a conservative operating limit, ensuring that neither batterywill overcurrent, or that the system will generally be able to providethe power required. Vehicle 202 can be an autonomous vehicle and in someinstances, vehicle 202 can use the limit data to determine a trajectoryof the vehicle 202 and/or adjust a driving characteristic/behavior ofthe vehicle 202.

The fault detection component 228 can determine a fault in the systembased at least in part on the battery data received from the respectiveBMSs. In some instances, the fault detection component 228 can usebattery data such as real-time current data to detect a fault. By way ofexample, if the first battery management system 208 transmits batterydata including real-time current data that exceeds a normal operatingthreshold, then the fault detection component 228 can determine that afault has occurred, identify a type of fault as a current overdrawfault, and/or generate an indication of the fault. In some instances,the fault detection component 228 can use battery data such as the limitdata to detect a fault. By way of example, if the first batterymanagement system 208 transmits battery data including a current limitat a value below a normal operating threshold, then the fault detectioncomponent 228 can determine that a fault has occurred, identify a typeof fault as a current limit fault, and/or generate an indication of thefault. Additionally, for purposes of illustration, the fault detectioncomponent 228 can use a battery state such as a shutdown fault statewithin the battery data. The fault detection component 228 can thendetermine that a fault has occurred, identify a type of fault as ashutdown fault state associated with a particular battery, and/orgenerate an indication of the fault.

The system controller(s) 230 can be configured to control steering,propulsion, braking, safety, emitters, communication, and other systemsof the vehicle 202. The system controller(s) 230 can communicate withand/or control corresponding systems such as drive module and/or othercomponents of the vehicle 202 such as the executive controller 218. Insome instances, the executive controller 218 can program and assignsystem controller(s) 230 and work in conjunction with one another.

The battery state component 232 can monitor and/or update the state ofthe first battery unit 204 and/or the second battery unit 210. In someinstances, the first battery unit 204, at the first battery managementsystem 208, can receive a command from the executive controller 218.Based on the current state of the first battery unit 204, the commandreceived by the executive controller 218, and/or present conditions(e.g., temperature, charge level, etc.), the battery state component 232can update the state of the first battery unit 204. For purposes ofillustration, if the current state of the first battery unit 204 is adriving state and the executive controller 218 transmits a chargecommand to the first battery unit 204 where it is received at the firstbattery management system 208, the battery state component 232 canchange the current state of the first battery unit 204 from a drivingstate to a charging state.

The battery status component 234 can monitor and/or update the status ofthe first battery 206 and/or the second battery 212. In some instances,the first battery 206 can indicate a normal status and the batterystatus component 234 can, via the first battery management system 208,broadcast an “okay” status. In some instances, the first batterymanagement system 208 can broadcast a “do not start” status, an “endmission” status, and/or a “stop immediately” status. The differentstatuses can inform other components such as the executive controller218 of an operational status of a battery and thus allow the executivecontroller 218 to adjust drive operations based on the status of thebattery or batteries.

The limit aggregation component 236 can provide different methods ofgenerating and/or calculating the aggregate data. In some instances, thelimit aggregation component 236 can be implemented in the first batteryunit 204 and/or the second battery unit 210. Additionally, the limitaggregation component 236 can be implemented in the vehicle computingsystem 216. Depending on the implementation, the limit aggregationcomponent 236 can be implemented in all or some of the executivecontroller 218, the first battery unit 204, the second battery unit 210,the vehicle computing system 216, and/or additional battery units. Insome instances, the limit aggregation component 236 can include an openloop component 238 and/or a closed loop component 240, with the openloop component 236 including an additive component 242 and/or a look-uptable component 244. In some case, the aggregate data can be based onfirst battery data and second battery data. In some instances, firstbattery data can include a first current limit associated with the firstbattery 206 and second battery data can include a second current limitassociated with the second battery 212.

The additive component 242 can calculate aggregate data by usingadditive properties. By way of example, the additive component 242 cansum the value of the first current limit and the value of the secondcurrent limit to generate an aggregate current limit. For example, if afirst current limit associated with the first battery 206 is 50 A andthe second current limit associated with the second battery 212 is 60 A,the additive component 242 can generate an aggregate limit of 110 A. Insome instances, the additive component 242 can calculate the aggregatecurrent limit using a weighted sum. For example, the first battery 206can have an associated first current limit of 100 A with a weight of0.70 and the second battery 212 can have an associated second currentlimit of 200 A with a weight of 0.30, and thus the additive component242 can generate an aggregate current limit of ((100 A*0.80)+(200A*0.30))=140 A.

The look-up table component 244 can use a database with entries where,in some instances, the first current limit and the second current limitfunction as a key or a reference to another value which can be used asthe aggregate current limit. For example, if a first current limitassociated with the first battery 206 is 50 A and the second currentlimit associated with the second battery is 60 A, the look-up tablecomponent 244 can look up a table indicating that the aggregate limit is100 A (or any value, depending on the implementation). In someinstances, the table can be associated with a battery and provided as,for example, a configuration file. In other instances, the table can be,for example, derived by performing a characterization of a battery. Inother instances, the table can be derived by data collection duringoperation of a battery.

The closed loop component 240 can use real-time data about the one ormore batteries, such as, but not limited to, internal impedance data. Insome instances, the closed loop component 240 can use a first impedanceassociated with the first battery unit 204 and a second impedanceassociated with the second battery unit 210 and calculate an aggregatecurrent limit using the first impedance, the second impedance, the firstcurrent limit, and the second current limit. In at least some examples,such current limits may be calculated, for example, in accordance with acurrent divider model.

As shown in FIG. 2, the vehicle 202 can be configured to use a chargingsystem 246 for charging the first battery 206 and/or the second battery212 coupled to the vehicle 202. The charging system 246 can include acharge coupler 248 to couple to a corresponding receptacle on theunderbody of the vehicle 202. The charge coupler 248 can have a housing250 which includes electrical contacts 252 and 254. The charge couplecan include a cable 256 which is coupled to a power source 258.Additional details of the charging system 246 are discussed in U.S.application Ser. No. 15/837,862 which is herein incorporated byreference.

As shown in FIG. 2, the charging system 246 may also include an anchor260 associated with the surface on which the charge coupler 248 ispositioned and configured to selectively hold the charge coupler 248 inposition. In some instances, the charge coupler 248 can be intended tobe either portable or fixed in location on the surface, and the anchor260 can be configured to selectively secure the charge coupler 248 in afixed position or permit its repositioning using, for example, knownsecurement assemblies, such as fasteners, clamps, etc.

The vehicle 202 can be maneuvered to a position over the charge coupler248, such that the electrical contacts 252 and 254 of the charge coupler248 align with contacts attached to the bottom of vehicle 202. Thevehicle 202 can be an autonomous vehicle and the charging system 246 caninclude one or more markers that can be used by the vehicle 202 tomaneuver into a substantially aligned position to receive a charge fromcharging system 246. In at least some examples, the autonomous vehiclemay be manually controlled onto such charging platform. The details ofsuch manual control of an autonomous vehicle are discussed in U.S.application Ser. No. 15/833,695 which is herein incorporated byreference.

In some instances, the vehicle 202 can be a driverless vehicle, such asan autonomous vehicle configured to operate according to a Level 5classification issued by the U.S. National Highway Traffic SafetyAdministration, which describes a vehicle capable of performing allsafety-critical functions for the entire trip, with the driver (oroccupant) not being expected to control the vehicle at any time. In suchexamples, because the vehicle 202 can be configured to control allfunctions from start to completion of the trip, including all parkingfunctions, it may not include a driver and/or controls for driving thevehicle 202, such as a steering wheel, an acceleration pedal, and/or abrake pedal. This is merely an example, and the systems and methodsdescribed herein may be incorporated into any ground-borne, airborne, orwaterborne vehicle, including those ranging from vehicles that need tobe manually controlled by a driver at all times, to those that arepartially or fully autonomously controlled.

Although the vehicle 202 has four wheels, the systems and methodsdescribed herein may be incorporated into vehicles having fewer or agreater number of wheels, tires, and/or tracks. The vehicle 202 can havefour-wheel steering and can operate generally with equal performancecharacteristics in all directions, for example, such that a first end262 of the vehicle 202 is the front end of the vehicle 202 whentravelling in a first direction 264, and such that the first end 262becomes the rear end of the vehicle 202 when traveling in the opposite,second direction 266, as shown in FIG. 2. Similarly, a second end 268 ofthe vehicle 202 is the front end of the vehicle 202 when travelling inthe second direction 266, and such that the second end 268 becomes therear end of the vehicle 202 when traveling in the opposite, firstdirection 264. These example characteristics may facilitate greatermaneuverability, for example, in small spaces or crowded environments,such as parking lots and urban areas.

The vehicle 202 may travel through the environment, relying at least inpart on sensor data indicative of objects in the environment in order todetermine trajectories of the vehicle 202. In some instances, as thevehicle 202 travels through the environment, one or more of the sensors270 capture data associated with detected objects (e.g., vehicles,pedestrians, buildings, barriers, etc.). The sensors 270 can includeimage capture devices, LIDAR sensors, SONAR sensors, RADAR sensors,microphones, or the like. The data captured by the sensors 270 can beused, for example, as input for determining trajectories for the vehicle202.

FIG. 3 is a schematic view of a vehicle 300 comprising a body module (orbody unit) 302, a first drive module (or first drive unit) 304 and asecond drive module (or second drive unit) 306 disposed at opposite endsof the body module 302. FIG. 3 illustrates the vehicle 300 in anunassembled state 308 and an assembled state 310. In the unassembledstate 308, the body module 302 can be supported by supports that areinternal or integrated into the vehicle 300, or that are built into aservice center, or the like.

During installation, in some instances, the first drive module 304 andthe second drive module 306 can be installed by moving them toward thebody module 302 in a longitudinal direction of the vehicle 300, as shownby arrows 312 and 314. Upon installing the drive module 304 and 306 withthe body module 302, a first battery unit 316 included in the firstdrive module 304 and a second battery unit 318 included in the seconddrive module 306 can be electrically coupled via a bus or a controllerarea network (CAN). In some instances, the first drive module 304 andthe second drive module 306 can be installed by moving them towards thebody module 302 in a vertical direction (and is not limited to thehorizontal coupling illustrated in FIG. 3). Additionally, in someinstances, the first drive module 304 and the second drive module 306can be substantially similar such that they can be interchanged in thebody module 302 and continue normal operation. In some instances, thefirst drive module 304 and the second drive module 306 can besubstantially different while having a substantially similar interface.In such an instance, the first drive module 304 and the second drivemodule 306 can provide different capabilities or limits but can stillcouple to the body module 302 interchangeably.

FIG. 4A depicts an example architecture of a redundant BMS architectureusing a ring configuration or topology 400. In some instances, one ormore executive controllers 402 can be coupled to a first batterymanagement system 404 and a last or nth battery management system 404.Though depicted in between the BMSs for illustrative purposes, any oneor more of the executive controllers 402 may be interspersed between theBMSs. In such an instance, the executive controller 402 may not bedirectly coupled to the second battery management system 406.Additionally, this configuration 400 allows for continued operation inthe case of particular fault scenarios. In some instances, the systemcan continue operations if any one coupling between neighboringcomponents is damaged and/or severed. This provides for the system tocontinue operation, though performance may be degraded, through multipletypes of fault conditions. In such a configuration, each BMS may receivelimit data and/or physical parameters from other BMSs and calculate oneor more aggregate limits to pass on to the one or more ECs 402. In turn,any one or more of the executive controllers 402 may receive theaggregate limits from multiple sources and, in at least some examples,relay individual BMS data to the remaining BMSs along the ring. Thisfigure illustrates an example configuration and other configurations arecontemplated. In some instances, the executive controller 402 can beconnected to additional battery management systems and not all batterymanagement systems may be coupled to the ring.

FIG. 4B depicts an example architecture of a redundant BMS architectureusing a mesh configuration 408. In some instances, an executivecontroller 410 can be coupled to a first battery management system 412,a second battery management system 414, a third battery managementsystem 416, and a last or nth battery management system 418. In such aninstance, the executive controller 410 can be coupled to every batterymanagement system, with each battery management system being coupled totwo other battery management systems. In some instances, the system cancontinue operations under fault conditions such as damaging or severingN−1 number of couplings of the executive controller 410. For purposes ofillustration, if the nth battery management system 418 is the fourthbattery management system, the system can continue operation if three ofthe four couplings to the executive controller 410 are damaged and/orsevered. Additionally, the configuration 408 can continue operationthrough a multitude of damaging or severing of couplings between batterymanagement systems. In such an example, each BMS may relay limit and/orparameter data to at least one or more of the other BMSs, as well as theexecutive controller 410. Each of the BMSs may, in turn, calculate anaggregate limit to be sent, in turn, to the executive controller 410.This figure illustrates an example configuration and otherconfigurations are contemplated. In some instances, the executivecontroller 410 may not be connected to every battery management systemand only a subset of the available battery management systems. In someinstances, the configuration can implement a full mesh topology wherethe executive controller 410 is coupled to every battery managementsystem and every battery management system is coupled to every otherbattery management system.

FIGS. 5-7 illustrate example processes in accordance with embodiments ofthe disclosure. These processes are illustrated as logical flow graphs,each operation of which represents a sequence of operations that can beimplemented in hardware, software, or a combination thereof. In thecontext of software, the operations represent computer-executableinstructions stored on one or more computer-readable storage media that,when executed by one or more processors, perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types. Theorder in which the operations are described is not intended to beconstrued as a limitation, and any number of the described operationscan be combined in any order and/or in parallel to implement theprocesses.

FIG. 5 depicts an example process 500 for receiving battery data andinstructing battery units. At operation 502, the process 500 can includereceiving, at an executive controller (EC), first battery data and firstaggregate battery data from a first battery unit. As discussed above,the EC can be coupled to the first battery unit. In some instances, thefirst battery data can comprise current limit data, power limit data,voltage limit data, temperature data, connection data, a system state, abattery state, a battery status, and/or impedance data. In someinstances, the aggregate battery data can include any combination ofdata or calculation of data including any of the battery data describedherein. At operation 504, the process 500 can include receiving, at theEC, second battery data and second aggregate battery data from a secondbattery unit. Similarly, as discussed above, the EC can be coupled tothe second battery unit. While depicted as operating in parallel (e.g.,substantially simultaneously within technical tolerances), operations502 and 504 can occur serially with either operation 502 or 504occurring before the other.

At operation 506, the process 500 can include generating, at the EC, acomparison between the first aggregate battery data and the secondaggregate battery data. The comparison can indicate whether the firstaggregate battery data has a greater value than the second aggregatebattery data, or vice versa.

At operation 508, the process 500 can include selecting, based on thecomparison, an operational battery data. In some instances, operation508 selects the lower aggregate battery data (e.g., also referred to asan aggregate battery limit) as the operational battery data (e.g., alsoreferred to as an operational limit). In some instances, operation 508selects the higher aggregate battery data as the operational batterydata. For purposes of illustration, under normal operation, the systemmay use a conservative setting and select the lower aggregate batterydata as the operational battery data. When the aggregate battery datacomprises current limits, using the conservative setting and selectingthe lower aggregate current limit can reduce the probability of drawingtoo much current from the batteries and, in turn, reduce the probabilityof damaging the battery unit, the battery, and/or the battery managementsystem. Additionally, for purposes of illustration, under criticalconditions, the system may need an increase in power and may select thehigher aggregate battery data as the operational battery data. Thehigher aggregate battery data can represent an optimistic availablepower and allow the system to possibly stress the components of thesystem because of the critical conditions of the environment orotherwise.

At operation 510, the process 500 can include transmitting, from the EC,the first battery data to the second battery unit and at operation 512,transmits, from the EC, the second battery data to the first batteryunit. This allows the first battery unit to receive the second batteryunit data and the second battery unit to receive the first battery unitdata. Similar to operations 502 and 504, while depicted as occurring inparallel, operations 510 and 512 can occur serially with one operationoccurring before the other, or vice versa. Additionally, operations 502,504, 510, and 512 can represent ongoing processes that occur at anyfrequency. Therefore, in some instances, battery data and aggregatebattery data can be continuously transmitted to and from the firstbattery unit and the second battery unit while the EC can generatecomparisons and select operational battery data essentiallyindependently as it receives battery data.

At operation 514, the process 500 can include controlling an electricload based on the operational battery data. As discussed above, thesystem can provide electrical power to drive modules to maneuver, insome instances, an autonomous vehicle.

FIG. 6 depicts a process 600 for transmitting aggregate battery datafrom a battery management system, for example, to an executivecontroller and/or another battery management system. At operation 602,the process 600 can include generating, at a first battery managementsystem (BMS), first battery data. In this process, the first batterymanagement system can refer to the first BMS 104 as described withregard to FIG. 1. At operation 602, the first battery data, as discussedabove, can include current limit data, power limit data, voltage limitdata, temperature data, connection data, a state, a status, and/orimpedance data. The first BMS can also be configured to monitor and/ormeasure the battery and/or battery unit to generate the battery data.

At operation 604, the process 600 can include transmitting, from thefirst BMS, the first battery data to an executive controller (EC) and/ora second BMS. The EC can refer to the EC 102 and the second BMS canrefer to the second BMS 106, as described with regard to FIG. 1.Additionally, as described in FIG. 1, the first BMS can be coupled tothe executive controller and/or the second BMS. The coupling enables thefirst BMS to transmit the first battery data to either the executivecontroller or the second BMS.

At operation 606, the process 600 can include receiving, at the firstBMS, second battery data from the second BMS. As discussed in FIG. 1,the first BMS can receive the second battery data through a coupling ofthe first BMS and the second BMS. In some instances, the first BMS canreceive the second battery data from the EC.

At operation 608, the process 600 can include generating, at the firstBMS, aggregate battery data. The aggregate battery data can include anycombination of data or calculation of data including any of the batterydata described above. In some instances, the first battery data caninclude a first current limit and the second battery data can include asecond current limit. When generating the aggregate battery data, thefirst BMS can use the first current limit and the second current limitto generate the aggregate battery data as an aggregate current limit. Insome instances, the first aggregate current limit can comprise a sum ofthe first current limit and the second current limit. In some instances,the first aggregate current limit can comprise a table entry using thefirst current limit and the second current limit as a lookup key. Insome instances, the first aggregate current limit can comprise a dynamiccurrent limit based on observed characteristics of the first and/orsecond battery such as, but not limited to, an impedance, a slew rate,or an overshoot.

At operation 610, the process 600 can include transmitting, from thefirst BMS, the aggregate battery data to the EC and/or the second BMS.In some instances, the aggregate battery data can be an aggregatecurrent limit. The first BMS can use the coupling to then transmit theaggregate battery data to the EC and/or to the second BMS. In someinstances, the system may have additional controllers and/or batterymanagement systems. In such instances, the first BMS can be configuredto transmit the aggregate battery data to a subset of the components inthe architecture. In some instances, the first BMS can be configured tobroadcast the battery data to every component in the architecture.

FIG. 7 depicts an example process for determining a fault condition. Atoperation 702, the process 700 can include receiving, at the EC, batterydata (e.g., limits, status, temperature, etc.). The battery data canrefer to the battery data described, for example, with regard to FIG. 1.

At operation 704, the process 700 can include performing a check todetermine if the battery data meets or exceeds a threshold. In someinstances, the battery data can, as described above, contain aggregatecurrent data. In order to perform the operations required by the system,a minimum amount of current can be required. In some instances, theaggregate current data can meet or exceed the minimum amount of currentrequired. In such an instance, the process 700 can return to operation702. If the aggregate current data does not meet or exceed the minimumamount of current required, the process 700 can proceed to operation706.

At operation 706, the process 700 can include generating, at the EC, anindication of a fault. In some instances, the fault can be an availablecurrent lower than an amount of current requested for a particular driveoperation. In some instances, the fault can be an available currentlower than a preferred current (e.g., if a preferred current includes abuilt-in safety factor above an amount of requested current). Faults canalso include an indication of a damaged or severed coupling as well asother battery data rising above or falling below required or preferredoperational thresholds.

At operation 708, the process 700 can include controlling an electricload, for example but not limited to an electric motor, based at leastin part on the battery data. In some instances, after detecting a faultand generating an indication of a fault, the system can continue basicoperation and provide available power to, for example, an electricmotor. In some instances, the operation 708 can allow the system tooperate as a fully functional system yet with an indication of a faultwherein the fault is a warning or an indication of a possible futureerror.

Example Clauses

A: A system comprising: a first battery unit comprising a first batteryand a first battery management system (BMS); a second battery unitcomprising a second battery and a second BMS; and a controllercommunicatively coupled with the first BMS and the second BMS, whereinthe controller is configured to perform operations comprising: receivingfirst battery data and first aggregate limit data from the first BMS;receiving second battery data and second aggregate limit data from thesecond BMS; determining, based at least in part on the first aggregatelimit data and the second aggregate limit data, an operational limit;determining, based at least in part on the operational limit, a torquevalue of an electric motor; and controlling the electric motor based atleast in part on the torque value.

B: The system of paragraph A, wherein the first BMS is communicativelycoupled with the second BMS, and wherein the operations furthercomprise: transmitting the first battery data from the first BMS to thesecond BMS; and transmitting the second battery data from the second BMSto the first BMS, wherein the first aggregate limit data is determinedby the first BMS and based, at least in part, on the first battery dataand the second battery data, and wherein the second aggregate limit datais determined by the second BMS and based, at least in part, on thefirst battery data and the second battery data.

C: The system of paragraph A or B, wherein determining the operationallimit comprises: comparing, as a comparison, the first aggregate limitdata and the second aggregate limit data; and selecting, based at leastin part on the comparison, a lower aggregate limit as the operationallimit.

D: The system of any of paragraphs A-C, wherein the first battery datacomprises a first current limit or a first power limit associated withthe first battery and the second battery data comprises a second currentlimit or a second power limit associated with the second battery.

E: The system of paragraph D, wherein the first aggregate limit data orthe second aggregate limit data comprise at least one of: a combinationof the first current limit and the second current limit; a lookup-tableentry based at least in part on the first current limit and the secondcurrent limit; or a dynamic limit based on observed characteristics ofthe first battery or the second battery, the observed characteristicscomprising at least one of an impedance, a slew rate, or an overshoot.

F: The system of any of paragraphs A-E, wherein the operations furthercomprise: determining that an observed operating condition is within arange associated with the operational limit, wherein the observedoperating condition comprises at least one of a power use, current use,or a voltage use; and determining that a fault condition has occurred,the fault condition indicating that at least one of the first batteryunit or the second battery unit is malfunctioning.

G: A method comprising: receiving first battery data and first aggregatelimit data from a first battery unit; receiving second battery data andsecond aggregate limit data from a second battery unit; determining,based at least in part on the first aggregate limit data and the secondaggregate limit data, an operational limit; determining, based at leastin part on the operational limit, a load value; and controlling, basedat least in part on the load value, an electric device.

H: The method of paragraph G, wherein the electric device is a motor,further comprising: determining that the operational limit does not meetor exceed a threshold value; determining that a fault condition hasoccurred; and controlling the motor to execute a safe stop trajectoryfor a vehicle.

I: The method of paragraph H, wherein the vehicle comprises anautonomous vehicle.

J: The method of any of paragraphs G-I, further comprising: determining,based at least in part on the first aggregate limit data and the secondaggregate limit data, a lower aggregate limit; and selecting the loweraggregate limit.

K: The method of any of paragraphs G-J, further comprising: determiningthat the first aggregate limit data does not meet or exceed a thresholdlimit; and determining that the first battery unit is malfunctioning.

L: The method of any of paragraphs G-K, further comprising: transmittinga portion of the first battery data to the second battery unit.

M: The method of any of paragraphs G-L, wherein the first battery datacomprises at least one of: current limit data; power limit data; voltagelimit data; temperature data; connection data; a battery operationalstate; a system operational state; or a battery status.

N: A non-transitory computer-readable medium storing instructionsexecutable by a processor, wherein the instructions, when executed,cause the processor to perform operations comprising: receiving, at acontroller, first battery data from a first battery unit; receiving, atthe controller, second battery data from a second battery unit;determining, based at least in part on the first battery data and thesecond battery data, an operational limit; determining, based at leastin part on the operational limit, a load value of an electric component;and controlling, based at least in part on the load value, the electriccomponent.

O: The non-transitory computer-readable medium of paragraph N, whereinthe instructions, when executed, further cause the processor to performoperations comprising: receiving, at the controller, a first aggregatelimit data from the first battery unit and a second aggregate limit datafrom the second battery unit; determining, based at least in part on thefirst aggregate limit data and the second aggregate limit data, a loweraggregate battery limit; and selecting the lower aggregate batterylimit.

P: The non-transitory computer-readable medium of paragraph O, whereinthe first aggregate limit comprises at least one of: a combination ofthe first aggregate limit data and the second aggregate limit data; alookup-table entry based at least in part on the first aggregate limitdata and the second aggregate limit data; or a dynamic limit based atleast in part on observed characteristics of the first battery unit orthe second battery unit, the observed characteristics comprising atleast one of an impedance, a slew rate, or an overshoot.

Q: The non-transitory computer-readable medium of any of paragraphs N-P,wherein the instructions, when executed, further cause the processor toperform operations comprising: generating, based at least in part on thefirst battery data and the second battery data, an aggregate batterylimit.

R: The non-transitory computer-readable medium of any of paragraphs N-Q,wherein the instructions, when executed, further cause the processor toperform operations comprising: receiving, at the controller, firstaggregate limit data from the first battery unit and second aggregatelimit data from the second battery unit; determining that a differencebetween the first aggregate limit data and the second aggregate limitdata meets or exceeds a difference threshold; and determining a failureof a first coupling between the first battery unit and the controller ora second coupling between the second battery unit and the controller.

S: The non-transitory computer-readable medium of any of paragraphs N-R,wherein the instructions, when executed, further cause the processor toperform operations comprising; determining, based at least in part onthe first battery data or the second battery data, that a faultcondition has occurred, the fault condition comprising at least one of:a current fault; a power fault; a voltage fault; or a temperature fault.

T: The non-transitory computer-readable medium of any of paragraphs N-S,wherein the instructions, when executed, further cause the processor toperform operations comprising: transmitting a portion of the firstbattery data to the second battery unit; and transmitting a portion ofthe second battery data to the first battery unit.

While the example clauses described above are described with respect toone particular implementation, it should be understood that, in thecontext of this document, the content of the example clauses can also beimplemented via a method, device, system, a computer-readable medium,and/or another implementation.

Conclusion

While one or more examples of the techniques described herein have beendescribed, various alterations, additions, permutations and equivalentsthereof are included within the scope of the techniques describedherein.

In the description of examples, reference is made to the accompanyingdrawings that form a part hereof, which show by way of illustrationspecific examples of the claimed subject matter. It is to be understoodthat other examples can be used and that changes or alterations, such asstructural changes, can be made. Such examples, changes or alterationsare not necessarily departures from the scope with respect to theintended claimed subject matter. While the steps herein can be presentedin a certain order, in some cases the ordering can be changed so thatcertain inputs are provided at different times or in a different orderwithout changing the function of the systems and methods described. Thedisclosed procedures could also be executed in different orders.Additionally, various computations that are herein need not be performedin the order disclosed, and other examples using alternative orderingsof the computations could be readily implemented. In addition to beingreordered, the computations could also be decomposed intosub-computations with the same results.

What is claimed is:
 1. A system comprising: a first battery unitcomprising a first battery and a first battery management system (BMS);a second battery unit comprising a second battery and a second BMS; anda controller communicatively coupled with the first BMS and the secondBMS, wherein the controller is configured to perform operationscomprising: receiving first battery data and first aggregate limit datafrom the first BMS; receiving second battery data and second aggregatelimit data from the second BMS; determining, based at least in part onthe first aggregate limit data and the second aggregate limit data, anoperational limit; determining, based at least in part on theoperational limit, a torque value of an electric motor; and controllingthe electric motor based at least in part on the torque value.
 2. Thesystem of claim 1, wherein the first BMS is communicatively coupled withthe second BMS, and wherein the operations further comprise:transmitting the first battery data from the first BMS to the secondBMS; and transmitting the second battery data from the second BMS to thefirst BMS, wherein the first aggregate limit data is determined by thefirst BMS and based, at least in part, on the first battery data and thesecond battery data, and wherein the second aggregate limit data isdetermined by the second BMS and based, at least in part, on the firstbattery data and the second battery data.
 3. The system of claim 1,wherein determining the operational limit comprises: comparing, as acomparison, the first aggregate limit data and the second aggregatelimit data; and selecting, based at least in part on the comparison, alower aggregate limit as the operational limit.
 4. The system of claim1, wherein the first battery data comprises a first current limit or afirst power limit associated with the first battery and the secondbattery data comprises a second current limit or a second power limitassociated with the second battery.
 5. The system of claim 4, whereinthe first aggregate limit data or the second aggregate limit datacomprise at least one of: a combination of the first current limit andthe second current limit; a lookup-table entry based at least in part onthe first current limit and the second current limit; or a dynamic limitbased on observed characteristics of the first battery or the secondbattery, the observed characteristics comprising at least one of animpedance, a slew rate, or an overshoot.
 6. The system of claim 1,wherein the operations further comprise: determining that an observedoperating condition is within a range associated with the operationallimit, wherein the observed operating condition comprises at least oneof a power use, current use, or a voltage use; and determining that afault condition has occurred, the fault condition indicating that atleast one of the first battery unit or the second battery unit ismalfunctioning.
 7. A method comprising: receiving first battery data andfirst aggregate limit data from a first battery unit; receiving secondbattery data and second aggregate limit data from a second battery unit;determining, based at least in part on the first aggregate limit dataand the second aggregate limit data, an operational limit; determining,based at least in part on the operational limit, a load value; andcontrolling, based at least in part on the load value, an electricdevice.
 8. The method of claim 7, wherein the electric device is amotor, further comprising: determining that the operational limit doesnot meet or exceed a threshold value; determining that a fault conditionhas occurred; and controlling the motor to execute a safe stoptrajectory for a vehicle.
 9. The method of claim 8, wherein the vehiclecomprises an autonomous vehicle.
 10. The method of claim 7, furthercomprising: determining, based at least in part on the first aggregatelimit data and the second aggregate limit data, a lower aggregate limit;and selecting the lower aggregate limit.
 11. The method of claim 7,further comprising: determining that the first aggregate limit data doesnot meet or exceed a threshold limit; and determining that the firstbattery unit is malfunctioning.
 12. The method of claim 7, furthercomprising: transmitting a portion of the first battery data to thesecond battery unit.
 13. The method of claim 7, wherein the firstbattery data comprises at least one of: current limit data; power limitdata; voltage limit data; temperature data; connection data; a batteryoperational state; a system operational state; or a battery status. 14.A non-transitory computer-readable medium storing instructionsexecutable by a processor, wherein the instructions, when executed,cause the processor to perform operations comprising: receiving, at acontroller, first battery data from a first battery unit; receiving, atthe controller, second battery data from a second battery unit;determining, based at least in part on the first battery data and thesecond battery data, an operational limit; determining, based at leastin part on the operational limit, a load value of an electric component;and controlling, based at least in part on the load value, the electriccomponent.
 15. The non-transitory computer-readable medium of claim 14,wherein the instructions, when executed, further cause the processor toperform operations comprising: receiving, at the controller, a firstaggregate limit data from the first battery unit and a second aggregatelimit data from the second battery unit; determining, based at least inpart on the first aggregate limit data and the second aggregate limitdata, a lower aggregate battery limit; and selecting the lower aggregatebattery limit.
 16. The non-transitory computer-readable medium of claim15, wherein the first aggregate limit comprises at least one of: acombination of the first aggregate limit data and the second aggregatelimit data; a lookup-table entry based at least in part on the firstaggregate limit data and the second aggregate limit data; or a dynamiclimit based at least in part on observed characteristics of the firstbattery unit or the second battery unit, the observed characteristicscomprising at least one of an impedance, a slew rate, or an overshoot.17. The non-transitory computer-readable medium of claim 14, wherein theinstructions, when executed, further cause the processor to performoperations comprising: generating, based at least in part on the firstbattery data and the second battery data, an aggregate battery limit.18. The non-transitory computer-readable medium of claim 14, wherein theinstructions, when executed, further cause the processor to performoperations comprising: receiving, at the controller, first aggregatelimit data from the first battery unit and second aggregate limit datafrom the second battery unit; determining that a difference between thefirst aggregate limit data and the second aggregate limit data meets orexceeds a difference threshold; and determining a failure of a firstcoupling between the first battery unit and the controller or a secondcoupling between the second battery unit and the controller.
 19. Thenon-transitory computer-readable medium of claim 14, wherein theinstructions, when executed, further cause the processor to performoperations comprising; determining, based at least in part on the firstbattery data or the second battery data, that a fault condition hasoccurred, the fault condition comprising at least one of: a currentfault; a power fault; a voltage fault; or a temperature fault.
 20. Thenon-transitory computer-readable medium of claim 14, wherein theinstructions, when executed, further cause the processor to performoperations comprising: transmitting a portion of the first battery datato the second battery unit; and transmitting a portion of the secondbattery data to the first battery unit.